Proper symlink handling for layers and projects #60140
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR addresses #60135 and #19524 issues involving the incorrect handling of symlinks in QGIS when saving projects. There are two main contributions:
In
qgspathresolver.cpp
, two calls toQFileInfo::canonicalFilePath()
are replaced withQDir::cleanPath(fi.absoluteFilePath())
. When saving layer datasources, QGIS this preserves relative paths without inadvertently resolving symlinks."%_attachments.zip"
component of a .qgs project.QGIS deletes and recreates the .zip on each project save, removing the symlink if one exists. This PR ensures the symlink’s target is deleted and recreated instead, aligning with expected behavior when editing a symlinked file.
Several tests cover various symlink scenarios::
git-annex
.Disclaimer: While not many users will write to broken symlinks or use symlinked project files, this PR ensures QGIS behaves consistently on Linux systems. These fixes benefit users who rely on symlinks for dynamic data, distributed storage, or large-file workflows like git-annex.
Related PR: A complementary fix in qgspathresolver.cpp is submitted under #60109. Please consider merging them together and backporting to the latest version. These are very simple fixes.